Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[vRNI] [4.x] VMware on Cloud for AWS (VMC) Integration as a data source (65100)

Last Updated: 1/21/2019Categories: InformationalTotal Views: 3102Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

The purpose of this article is to provide guidance and general information on the VMware on Cloud for AWS (VMC) integration as a data source from vRealize Network Insight 4.0

Resolution

vRealize Network Insight 4.0 supports VMC on AWS for the enterprise license users only. You can add VMC vCenter or VMC NSX Manager as a data source

NI support for VMC is still in preview mode under VMC. It is suggested to work with NI Product management before enabling the same in your environment.
Definition of Preview : Ability for paying customers (i.e. customers running production workloads) to sign-up for the service or feature is constrained by VMware pending achievement of certain criteria (e.g. sufficient customer experience validation).

Adding VMC vCenter as a Data Source

Note: To add VMC vCenter as a data source, you need to have the Cloud Administrator privileges.

To obtain the credentials to add VMC NSX Manager as a data source, perform the following steps:

Log in to your VMWare Cloud Services console.

Click VMware Cloud on AWS under My Services.

Click the name of the desired SDDC.

In the Settings tab, copy the vCenter FQDN in the vCenter FQDN tab. From the Default vCenter User Account tab, copy the user credentials.

In the Accounts and Data Source page under Settings, click Add Source.

Under Public Clouds, click VMWare Cloud on AWS (vCenter).

In the Add a new VMware vCenter Account or Source of VMware Cloud on AWS page, provide the following information:

Select the Collector VM.

Provide the vCenter FQDN that you have retrieved from the VMware Cloud Services..

Provide the user credentials that you retrieved from the VMware Cloud Services.

Click Validate.

Enter Nickname and Notes (if any) for the data source and click Submit

Adding VMC NSX Manager as a Data Source

To obtain the credentials to add VMC NSX Manager as a data source, perform the following steps:

Log in to your VMWare Cloud Services console.

Click VMware Cloud on AWS under My Services.

Click the name of the desired SDDC.

From the Support tab, note the IP address of the NSX Manager.

Click the user profile name on the top right corner of the page.

Click the API Tokens tab and copy the Refresh Token.

In the Accounts and Data Source page under Settings, click Add Source.

Under Public Clouds, click VMWare Cloud on AWS (NSX Manager).

In the Add a new VMC NSX Manager Account or Source of VMware Cloud on AWS page, provide the following information:

Select the corresponding vCenter.

The collector is automatically selected based on the selection of the vCenter. VMC NSX Manager has to be added to the same collector VM as that of the corresponding vCenter.

Provide the IP address and the CSP Refresh Token.

Provide the user credentials.

Click Validate.

If you want to collect IPFIX flows for DFW, select Enable DFW IPFIX.

Enter Nickname and Notes (if any) for the data source and click Submit

Note:  Error messages pop up if the following conditions are not met:

To enable DFW IPFIX, you need to have the Cloud Administrator privileges

VMC NSX Manager allows only four collectors to be added to its DFW IPFIX collector profile

VMC for AWS Entities

Here are the entities related to VMC NSX Manager:

VMC NSX Manager Data Source

VMC NSX Manager

VMC Firewall

Some sample search queries related to the VMC entities are:

VMs where L2 Network = '' (L2 Network -> VMC Segment)

VMC Policy Based VPN where Tier0 = ''

VMC Policy Based VPN where Local Network = '' (Local Network of Policy Based VPN Rule)

VMC Policy Based VPN where Remote Network = '' (Remote Network of Policy Based VPN Rule)

VMC Group where Translated VM = ''

VM where VMC Group = ''

VMC Firewall Rule

VMC Segment

VMC Policy-Based VPN

VMC Group

Note : Currently, vRealize Network Insight does not support the following search query:

vmc group where members = <IP/VM/MEMBERSHIP_CRITERIA/CHILD GROUPS/IPSETS>

VMC does not support child groups or IPSETS. Hence all the searches like :

vmc firewall rule where Indirect __________ = '' or vmc group where Indirect _____= '' are disabled

VMC Deployment

vRealize Network Insight supports the following deployment models for VMC for AWS:

Collector deployed in VMC:

In this deployment model, the collector is deployed as a workload in Compute Gateway in VMC. The platform is deployed in the SDDC on-premises version.

The firewall rules of Management Gateway allow communication to VMC vCenter and VMC NSX Manager over HTTPS.

The collector communicates to the platform using the existing communication mechanisms over VPN or Direct Connect.

Collector and Platform deployed in the SDDC on-premises version

In this deployment model, the collector and the platform are deployed in the SDDC on-premises version.

The firewall rules of Management Gateway allow communication to vCenter and policy using HTTPS over VPN.

The VPN connectivity between SDDC (on-premises or SaaS version) and VMC allows data to be fetched by the collector.

The prerequisites for the above deployment models are:

There should be connectivity between the platform or collector (on-premises) and VMC SDDC. It could either be over VPN or DX if the vRealize Network Insight installation is in the private SDDC.

There should be a Management Gateway firewall rule to allow the collector to call the NSX Manager APIs over HTTPS (443).

Related Information

To access the FAQ on the VMware on Cloud for AWS (VMC) integration with vRealize Network Insight 4.0 / Network Insight 4.0, see the following kb :
https://kb.vmware.com/s/article/65112

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Network Insight

Related Versions:

Take Our Survey

Support Assistant